Proposed changes

Problem: In order to enable NAP WAF protection for NGF traffic, we need to install the nap module in the NGINX container, provide a mechanism to deploy the additional WAF v5 containers in the NGINX deployment, and then set the base app_protect_* directives in the NGINX conf

Solution:

1. Add the ability to build a NAP WAF image:

• Update the NGINX Plus Dockerfile to optionally install the app protect module when INCLUDE_NAP_WAF=true
• Extend the ENTRYPOINT script to create an additional required file
• Create an additional Make target to build the image

2. Extend the NGINXProxy resource to support WAF

• Add a toggle to enable waf in the NGINXProxy resource
• If enabled, deploy the additional waf containers
• Add support for user overrides of certain parameters of the waf containers (image, resources, additional volumes)
• If WAF is enabled, add the required base app_protect_* directives to the nginx conf (load module and enforcer address)

3. Extend the Helm chart to support these new configuration options

Notes:

• NAP v5 is supported in both OSS and Plus. This PR only adds Dockerfile support for Plus, but deploying an NGF compatible OSS image with the NAP module installed isn't blocked by this implementation
• Building the image and testing in the pipeline will be handled in a separate PR

Testing: Deployed in GKE (NAP WAF does not run on arm64 and we can't use emulated images locally, so deploying NAP requires an amd64 architecture). Created the NAP enabled image, used NGINXProxy to set WAF to true, used user provided images for the waf containers (I cached them to the GCP registry), and I mounted an additional volume to NGINX and waf-config-mgr for bundles (as we don't have the next part developed yet). Once deployed, I used kubectl cp to copy the bundle to the mounted volume. I used snippets to create the app protect directives at the server level, and checked that the firewall blocked the malicious appearing traffic.

Closes #3451
Closes #3453

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• [] I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE